home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 22
/
Cream of the Crop 22.iso
/
os2
/
adialin1.zip
/
ADIALIN.DOC
< prev
next >
Wrap
Text File
|
1996-10-04
|
34KB
|
690 lines
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ aDialIn - Dial-in server package for OS/2 │
│ - Version 1.10 - │
│ │
│ *** S H A R E W A R E *** │
│ │
│ D o c u m e n t a t i o n │
│ │
│ (C) 1996 Axel Mueller │
│ Email: amueller@stargate.rz.fh-offenburg.de │
│ Official FTP site: ftp://stargate.rz.fh-offenburg.de/aDialIn │
└────────────────────────────────────────────────────────────────────────────┘
The aDialIn package contains all dial-in services of the SIDIS/2 package
which I introduced 3 months ago. The SIDIS/2 package also contained
email services now available as aPOP3d package. (APOP3D??.ZIP)
While both packages will stay compatible to each other they are more easy
to set up.
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ Content │
│ │
└────────────────────────────────────────────────────────────────────────────┘
1. Legal stuff
2. Files included in this package
3. Features
4. System requirements
5. General Installation
6. User and programm administration (ACCOUNTS.EXE)
7. Client login scipts for OS/2, Windows 3.1, Windows 95/NT
8. Conclusion
APPENDIX A Network structure
APPENDIX B Work-around for routing bug in PPP.EXE
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 1. Legal stuff │
│ │
└────────────────────────────────────────────────────────────────────────────┘
IF YOU DOWNLOAD OR USE THIS PROGRAM YOU AGREE TO THESE TERMS.
Under no circumstances am I liable for any of the following:
1. third-party claims against you for losses or damages;
2. loss of, or damage to, your records or data; or
3. economic consequential damages (including lost profits or
savings) or incidental damages
I do not warrant uninterrupted or error free operation of the
Program. I have no obligation to provide service, defect
correction, or any maintenance for the Program. I have no
obligation to supply any Program updates or enhancements to you
even if such are or later become available.
THERE ARE NO WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 2. Files included in this package │
│ │
└────────────────────────────────────────────────────────────────────────────┘
ACCOUNTS.EXE user & programm administration
ADIALOS2.RSP Response script for OS/2 based dial-in client
ADIALW3.CMD Response script for Windwos 3.x based dial-in client
ADIALW95.SCP Response script for Windows 95/NT based dial-in client
ASHARED.DLL central module used by all EXEs/DLLs of aPOP3d package
MONTHTOT.CMD calculate total monthly on-line for each modem
PPP1.CFG PPP configuration file for modem 1
PPP2.CFG PPP configuration file for modem 2
PPP3.CFG PPP configuration file for modem 3
PPP4.CFG PPP configuration file for modem 4
REESTAB.CMD work-around for routing table bug in PPP.EXE
(explained in APPENDIX B)
RXIOCTL.CMD script for registration of RXIOCTL.DLL functions
RXIOCTL.DLL provision of REXX functions for asyncronous I/O
RXPRF.CMD script for registration of RXPRF.DLL functions
RXPRF.DLL provision of REXX functions for user database access
SWREG.EXE shareware registration utility
UC1.CMD activate modem 1
UC2.CMD activate modem 2
UC3.CMD activate modem 3
UC4.CMD activate modem 4
USERCTRL.CMD modem control script
USERCTRL.INI configuration file for modem control script
WAITXS.CMD REXX script causes the session to sleep for X seconds
WELCOME.MSG sample file for modem login message
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 3. Features │
│ │
└────────────────────────────────────────────────────────────────────────────┘
- central user database (USER.INI) for all user- and program-relevant
information
- user administration compatible with aPOP3d package (email server)
- uses PPP protocol (PPP.EXE not included in this package)
- supports as many modems as PPP.EXE does (up to 10)
- modem control implemented as REXX script and therefore highly configurable
(script runs once for each modem connected)
- user administration tool provides a lot of information about users
- tool for calculation of total on-line time for past month included
The aDialIn package has been used on a daily basis to provide efficient
and reliable Internet access to about 70 students (including myself).
Even using a not-state-of-the-art 486-DX/2-66 with 16 MB it serves
4 high speed modems (2x 28,8 kB, 2x 19,2 kB) well at high throughput
rates even with 4 simultanous PPP sessions.
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 4. System requirements │
│ │
└────────────────────────────────────────────────────────────────────────────┘
- Hardware suggestion: 486-DX/2-66 with 16 MB RAM
- OS/2 Merlin
* or *
OS/2 Warp Connect
* or *
OS/2 Warp Server
* or *
OS/2 Warp + TCP/IP 2.0 + CSD UN64092
- HPFS is *HIGHLY* recommended (otherwise the length of usernames is
restricted to 8 characters. FAT has not been tested!)
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 5. General Installation │
│ │
└────────────────────────────────────────────────────────────────────────────┘
1. Use the following hints to place the files included in this package in
the correct directories:
ACCOUNTS.EXE a directory in your PATH (recommended: \TCPIP\BIN)
ASHARED.DLL a directory in your LIBPATH (recommended: \TCPIP\DLL)
MONTHTOT.CMD same diretory as USERCTRL.CMD (recommended: \USERCTRL)
PPP1.CFG directory defined in ETC variable
You may try "echo %ETC%" to check where your ETC
variable points to
PPP2.CFG "
PPP3.CFG "
PPP4.CFG "
REESTAB.CMD same diretory as USERCTRL.CMD (recommended: \USERCTRL)
RXIOCTL.CMD a directory in your PATH (recommended: \TCPIP\BIN)
RXIOCTL.DLL a directory in your LIBPATH (recommended: \TCPIP\DLL)
RXPRF.CMD a directory in your PATH (recommended: \TCPIP\BIN)
RXPRF.DLL a directory in your LIBPATH (recommended: \TCPIP\DLL)
SWREG.EXE a directory in your PATH (recommended: \TCPIP\BIN)
UC1.CMD same diretory as USERCTRL.CMD (recommended: \USERCTRL)
UC2.CMD same diretory as USERCTRL.CMD (recommended: \USERCTRL)
UC3.CMD same diretory as USERCTRL.CMD (recommended: \USERCTRL)
UC4.CMD same diretory as USERCTRL.CMD (recommended: \USERCTRL)
USERCTRL.CMD directory defined in USERCTRLDIR variable
You may try "echo %USERCTRLDIR%" to check where your
USERCTRLDIR variable points to (see Chapter 5.2)
USERCTRL.INI same diretory as USERCTRL.CMD (recommended: \USERCTRL)
WAITXS.CMD a directory in your PATH (recommended: \TCPIP\BIN)
WELCOME.MSG same diretory as USERCTRL.CMD (recommended: \USERCTRL)
2. Make sure that the following environment variables are set in
CONFIG.SYS:
SET ETC=c:\mptn\etc
The ETC variable is most likely already set. If this is the case
you don't have to change it.
SET USERCTRLDIR=C:\USERCTRL
The USERCTRLDIR variable defines the directory for the main
components of this package.
SET MAILDIR=C:\MAIL
This definition is only needed if you also have the aPOP3d package
installed and want to let the users know the mailbox count during
the modem login stage.
The MAILDIR variable points to the base mail directory under which
all the user mail directories (mailboxes) will be created.
Make sure that this directory exists; otherwise no user mail
directories can be created.
3. Verify that a COM port driver is installed and that every COM port
has been set to a unique IRQ which you must tell to the COM port
driver:
DEVICE=C:\OS2\BOOT\COM.SYS (1,3F8,4) (2,2F8,3) (3,3E8,11) (4,2E8,12)
As you can see I'm using COM.SYS provided by IBM. You don't have to
use special COM drivers (like SIO.SYS) if you use 4 modems.
4. Verify that every COM ports is set to the correct speed. I set the
COM port parameters in CONFIG.SYS as follows:
CALL=C:\OS2\MODE.COM COM1:57600,N,8,1,TO=OFF,XON=OFF,OCTS=ON,RTS=HS,
DTR=ON,IDSR=OFF,ODSR=OFF,BUFFER=ON
Note that in CONFIG.SYS all parameters have to be in the same line as
the CALL command belongs to. (not as shown above)
5. Each of the REXX scripts for modem control (USERCTRL.CMD) runs in
a session of CMD.EXE. This makes it difficult to know which modem
is served by which session (e.g. if you want to kill one of the sessions
only). To overcome this you simply have to create unique copies of
CMD.EXE. To do this type at the OS/2 prompt, while you are in the \OS2
directory:
copy cmd.exe cmd1.exe
copy cmd.exe cmd2.exe
copy cmd.exe cmd3.exe
copy cmd.exe cmd4.exe
The digit in the filename indicates the COM port to which the modem
is connected, e.g. if you have only 2 modems on COM3 and COM4 you will
need CMD3.EXE and CMD4.EXE which will be started respectively by UC3.CMD
and UC4.CMD.
6. Before you can use the main REXX script for modem control the DLLs
needed by the script have to be registered. This is done by RxPRF.CMD
and RxIOCTL which should be called once during startup, e.g. by
putting the lines "call RxPRF.CMD" and "call RxIOCTL.CMD" in STARTUP.CMD
on your boot drive. If you also want to start-up modem control from
STARTUP.CMD, during boot-up, then for a machine with 3 modems connected
your STARTUP.CMD should include this:
REM Register DLLs ...
call rxprf.cmd
call waitXs 2
call rxioctl.cmd
call waitXs 2
cd c:\userctrl
REM Start control for modem 1 ...
call uc1.cmd
call waitXs 2
REM Start control for modem 2 ...
call uc2.cmd
call waitXs 2
REM Start control for modem 3 ...
call uc3.cmd
7. There is a configuration file USERCTRL.INI in the directory where
your USERCTRLDIR variable points to. In contains a number of parameters
used to adapt the aDialIn package to your preferences:
LogPath = c:\userctrl\log
This directory will contain all the log files produced.
Make sure that this directory exists; otherwise no log files can
be created.
FirstModemCOM = 1
This is the COM port where your first modem is connected to.
LastModemCOM = 4
This is the COM port where your last modem is connected to.
ModemInitString = ATZQ0V1S0=0S3=13S4=10S7=60S10=7
This is the init string to initialize the modems.
Note that you have to set up your modem to NO ECHO (e.g. ATE0)
and store this setting in the modem CMOS (e.g. AT&W).
WelcomeFile = welcome.msg
The content of this file will be sent to the peer right after
the modem connect. In this file you may use $DATE$ and $TIME$
as macros which will be replaced by current values during
transmission.
You should adapt the content of this file for your preferences.
ShowWelcomeScreen = 1
Toggles transmission of WelcomeFile ON (1) or OFF (0).
ShowLastLogin = 1
Toggles transmission of last login date during the login stage
ON (1) or OFF (0).
ShowMailboxStatus = 1
Toggles transmission of users mailbox count during the login
stage ON (1) or OFF (0).
This feature is designed for use with the aPOP3d package which
acts as a email server.
ShowLineUsage = 1
Toggles transmission of names of current users of other modem
lines on this system during the login stage ON (1) or OFF (0).
PPPWorkAround = 1
Use work-around for routing table bug in PPP.EXE which is
explained in APPENDIX B.
8. Since the dial-up machine isn't connected directly to the ethernet all
other machines on this ethernet have to know how to reach the dial-up
host. This will be done by pulishing an ARP (Address resolution protocol)
entry. There has to be one entry for each dial-up host (which equals the
number of modems installed on the dial-in server). A good place for the
appropriate commands is TCPEXIT.CMD which you should create or append to
in the \TCPIP\BIN directory.
The ARP command is followed by the parameter "-s", then the IP
number of the dial-up host, next comes the ethernet address of
the dial-in server's ethernet adaptor and finally the "pub" parameter
is required.
If you have 4 modems and IP numbers according to the NETWORK STRUCTURE
sketch in APPENDIX A, your TCPEXIT.CMD might look like this:
REM Add arp entries for remote hosts (via modem connected)
arp -s 111.222.333.11 00:00:C0:04:F7:37 pub
arp -s 111.222.333.12 00:00:C0:04:F7:37 pub
arp -s 111.222.333.13 00:00:C0:04:F7:37 pub
arp -s 111.222.333.14 00:00:C0:04:F7:37 pub
Make sure that there is either no "ipgate" statement or an "ipgate=on"
statement in \TCPIP\BIN\TCPSTART.CMD. Using "ipgate=off" the dial-in
server will not gate any IP packets to the dial-up machine!
9. Depending on the number of modems installed on your dial-in server
you have to configure the appropriate PPP config file e.g. PPP1.CFG
for the modem connected to COM1, PPP2.CFG for the modem connected to
COM2 etc..
Only line 3 of each of the configuration files needs changing.
Line 3 should have IP number of you dial-in server, then a colon,
followed by the IP number of your dial-up machine (the same
IP number as you have put in your TCPEXIT.CMD before in order to
publish an ARP entry for).
Again you should have a look at the NETWORK STRUCTURE sketch in
APPENDIX A to get a clearer picture.
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 6. User and programm administration (ACCOUNTS.EXE) │
│ │
└────────────────────────────────────────────────────────────────────────────┘
Before any user can dial ina record for this user has to be created.
If you type "accounts" without any parameters (or wrong parameters)
a syntax description will be displayed:
------------------------------------------------------------------------------
H:\Dev>accounts
aCCOUNTS - User administration for aPOP3d and aDialIn v1.10/Sep 8 1996
(C) 1996, Axel Mueller (amueller@stargate.rz.fh-offenburg.de)
=== Usage: ===================================================================
-a <user> <password> <Real name> -l[m[a|c|f|j|n|o|p|r|s|t|u]]
-d <user> -m [<user> <name> <program> <subject>]
-ds -n <user> [subject]
-e [size] -p <user> <password>
-f <user> [forward address] -r <user>
-fc <user> [forward address] -s <user> [size]
-i -sd [size]
-l[d[a|l|n|t|r|u]
=== Explanation: =============================================================
-a add user -d display user record -ds display settings -e set
encryption size -f activate mail forward -fc activate copy forward
-i display registration information -ld list dial-in related information
of all users; display: dAys since last login, Numbered list, on-line time of
Last month, Total on-line time, Real name, Username -lm list Mail related
information of all users; display: Age of mails, mailbox Count, Forward address,
notification subJect, Numbered list, forward cOunt, days since last Pop3 check,
Real name, mailbox Size, notification counT, Username (only one UPPER letter=
sort criteria; following "-" will cause reverse order) -m define mail
processor -n activate sender notification -p assign password to user
-r remove user -s set max mailbox size -sd set max mailbox size default
------------------------------------------------------------------------------
┌─────────────────────────────────────────────────────────┐
│ Add user record │
└─────────────────────────────────────────────────────────┘
accounts -a <user> <password> <Real name>
Note that the username "system" is reserved for the mail processor
of the aPOP3d package.
<user>
... Username the user will be assigned
This also determines the email address of the user to
"user@hostname.domainname" in the aPOP3d package.
<password>
... Password is used to authenticate user during modem login
and also for email retrieval via POP3. It must contain
only digits and letters (no spaces etc.)
Note that the password is case sensitive!
<Real Name>
... This is the real name of the user. There may be spaces between
first, middle and last name.
You will get a confirmation of the newly created user:
------------------------------------------------------------------------------
H:\Dev>accounts -a smith terraX Robert Smith
aCCOUNTS - User administration for aPOP3d and aDialIn v1.10/Sep 8 1996
(C) 1996, Axel Mueller (amueller@stargate.rz.fh-offenburg.de)
User smith created.
New password for user smith has been assigned.
------------------------------------------------------------------------------
┌─────────────────────────────────────────────────────────┐
│ Display user record │
└─────────────────────────────────────────────────────────┘
accounts -d <user>
<user>
... Username the user the record should be displayed for
------------------------------------------------------------------------------
H:\Dev>accounts -d smith
aCCOUNTS - User administration for aPOP3d and aDialIn v1.10/Sep 8 1996
(C) 1996, Axel Mueller (amueller@stargate.rz.fh-offenburg.de)
*** User record per 12.08.1996 13:01:01 ***
GENERAL
User: Robert Smith (smith)
Record created: 08.04.1996 22:33:31
Last password change: 08.04.1996 22:33:32
DIAL IN
First/last login: 09.04.1996 17:10:07 / 25.09.1996 20:00:26
Login total/last month: 00693x(00098:06:23) / 0098x(014:25:01) (h:m:s)
------------------------------------------------------------------------------
┌─────────────────────────────────────────────────────────┐
│ Display registration information │
└─────────────────────────────────────────────────────────┘
accounts -i
------------------------------------------------------------------------------
H:\Dev\bin>accounts -i
aCCOUNTS - User administration for aPOP3d and aDialIn v1.10/Sep 8 1996
(C) 1996, Axel Mueller (amueller@stargate.rz.fh-offenburg.de)
*** Registration information per 12.08.1996 15:52:43 ***
aPOP3d: registered for FH Offenburg, Standort Gengenbach
aDialIn: no (valid) registration found
------------------------------------------------------------------------------
┌─────────────────────────────────────────────────────────┐
│ Display user list │
└─────────────────────────────────────────────────────────┘
accounts -l[d[a|l|n|r|t|u]]
-l ... displays a list containing username and real name of all users
-ld ... display a list of dial-in related information; if no further flag
is set the list will contain only username and real name
The -ld parameter may be followed by one or more of the following flags:
a ... days since last login
l ... on-line time of the last month the user has dialed in
n ... number the users in list
r ... real name of user
t ... total on-line time since the user record was created
u ... username
The columns are in the same order as the flags following the -ld parameter.
The flags have to be in lower case. However you may put _one_ letter in
upper case which will result in a sorted list with the uppercase letter
beeing the sort criteria. If you want the sorted list in reverse order
simply put a "-" sign behind the uppercase letter.
------------------------------------------------------------------------------
H:\Dev\bin>accounts -ldurL
aCCOUNTS - User administration for aPOP3d and aDialIn v1.10/Sep 8 1996
(C) 1996, Axel Mueller (amueller@stargate.rz.fh-offenburg.de)
*** User list per 04.10.1996 19:08:08 ***
Username Real name Last month
----------------------------------------------------------
aherrmann Axel Herrmann 15:57:47
amueller Axel Mueller 14:25:01
meisenmann Martin Eisenmann 4:46:28
hkern Hansi Kern 0:42:05
dmannes Delf Mannes -:--:--
----------------------------------------------------------
35:51:21
------------------------------------------------------------------------------
┌─────────────────────────────────────────────────────────┐
│ Assign (new) password to user │
└─────────────────────────────────────────────────────────┘
accounts -p <user> <password>
<user>
... Username for to which the password should be assigned
<password>
... New password which should be assigned to the user
------------------------------------------------------------------------------
H:\Dev\bin>accounts -p smith newPassword
aCCOUNTS - User administration for aPOP3d and aDialIn v1.10/Sep 8 1996
(C) 1996, Axel Mueller (amueller@stargate.rz.fh-offenburg.de)
New password for user smith has been assigned.
------------------------------------------------------------------------------
┌─────────────────────────────────────────────────────────┐
│ Remove user │
└─────────────────────────────────────────────────────────┘
accounts -r <user>
<user>
... Username which should be removed
This command removes the compley user record from the user database.
------------------------------------------------------------------------------
H:\Dev\bin>accounts -r smith
aCCOUNTS - User administration for aPOP3d and aDialIn v1.10/Sep 8 1996
(C) 1996, Axel Mueller (amueller@stargate.rz.fh-offenburg.de)
User smith removed.
------------------------------------------------------------------------------
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 7. Client login scipts for OS/2, Windows 3.1, Windows 95/NT │
│ │
└────────────────────────────────────────────────────────────────────────────┘
At our local campus we have dial-in users using OS/2, Windows 3.1,
Windows 95 and Windows NT. For an efficient time-saving login procedure
it is important to use a script for dial-in. Therefore I have included
the scripts the students of our local campus use for dialling into our
aDialIn package equipped machine:
*** OS/2 *** (script file: aDialOS2.RSP)
You should get a copy of PPPDIAL.CMD (available on many FTP servers as
PPDIAL29.ZIP - featuring automatic redial if line is busy) and create a
new provider in the DIAL OTHER INTERNET PROVIDERS notebook.
Enter the Login ID and password an check the "required" box.
In the Phone number field you can specify different phone numbers.
These numbers will be dialed one after another if a line is busy.
In the login sequence field you should specify
"pppdial.cmd c:\mptn\etc\aDialOS2.RSP" (change drive and directory if
necessary). Make sure PPPDIAL.CMD is in a directory included in your
PATH statement. All other settings in the notebook should be obviously.
*** Windows 3.1x *** (script file: aDialW3.CMD)
This script is for use with Trumpet WinSock. Just copy it to the
directory where your Trumpet WinSock resides.
*** Windows 95 *** (script file: aDialW95.SCP)
This script has to be used with the DIAL UP NETWORK. I know that it works
but I don't know how (since I do not use Windows 95).
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ 8. Conclusion │
│ │
└────────────────────────────────────────────────────────────────────────────┘
I have tried my best to make this documentation better than the one I
provided in the SIDIS/2 package. But it is always difficult to explain
things to someone when you are familiar with it and the others are not.
If you experience any problems the easiest and fastest way to overcome
them is to drop me an email. Under normal circumstances you should
receive an answer within one day (of course solving the problem may
take longer)
I regulary monitor the Internet news group comp.os.os2.networking.tcp-ip
as well.
Keep in mind - I rely on the feedback I get ;-))
Axel Mueller
amueller@stargate.rz.fh-offenburg.de
09/30/96
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ APPENDIX A: Network structure │
│ │
└────────────────────────────────────────────────────────────────────────────┘
<--------------- DOMAIN: modem-domain.com ----------------------------------->
┌─────────────────┐ LAN
│ remote "host1" │ (Net 111.222.333)
│ 111.222.333.11 │-Modem--(Telephon network)--Modem1---. ---
└─────────────────┘ | |
| |
┌─────────────────┐ | |
│ remote "host2" │ | |
│ 111.222.333.12 │-Modem--(Telephon network)--Modem2-. | |
└─────────────────┘ | | |
| '-┌──────────────────┐
'---│ "modem-host" │
.---│ 111.222.333.10 │
| .-│ Ethernet Address │
┌─────────────────┐ | | │ 00:00:C0:04:F7:37│
│ remote "host3" │ | | │ │
│ 111.222.333.13 │-Modem--(Telephon network)--Modem3-' | └──────────────────┘
└─────────────────┘ | |
| |
┌─────────────────┐ | ┌─────────────────┐
│ remote "host4" │ | │ default router │
│ 111.222.333.14 │-Modem--(Telephon network)--Modem4---' │ 111.222.333.254 │
└─────────────────┘ └─────────────────┘
|
'---<INTERNET>
┌────────────────────────────────────────────────────────────────────────────┐
│ │
│ APPENDIX B: Work-around for routing bug in PPP.EXE │
│ │
└────────────────────────────────────────────────────────────────────────────┘
Unfortunately there is a routing bug in PPP.EXE since it went "gamma"
(2 years ago). Obviously IBM is testing PPP.EXE only with one single
PPP connection at a time. The bug only becomes visible if you have
mutliple simultanous PPP sessions. In this case it may happen that
the routing table entry for one already active PPP session will be
removed if another PPP session starts. The modem link will still be up
but there is no TCP/IP connection to the network (and even to the modem
server) anymore. I have informed IBM Corp. in the USA but they told me
the IBM Germany is responsible. For the latter I was not able to locate
somebody I could report this bug to. That's the way thing will improve
soon ...
Anyway - I have implemented a "small & dirty" work-around which is
better than loosing your network connection from time to time.
You will need two programs called "netstat.exe" and "ifconfig.exe"
which are part of TCP/IP, Warp Connect and Warp Server. They already
should be in the PATH.
Some seconds before a new PPP.EXE will be started, the modem control
script (USERCTRL.CMD) will start "netstat.exe". The output (content of
the routing table) will be redirected to a file. Afterwards it will
start another another script (REESTAB.CMD) which will wait for
5 seconds (during this time the new PPP.EXE will have been established)
and then re-configure the PPP interfaces (according to the routing table
from the file) that were in existence before the new PPP.EXE was started.
The REESTAB.CMD script will only be started if somebody dials in and there
is already one or more active PPP sessions.